Skip to content

docs: add FAQ section for common questions#3030

Closed
meichuanyi wants to merge 1 commit into
openai:mainfrom
meichuanyi:docs/add-faq-section
Closed

docs: add FAQ section for common questions#3030
meichuanyi wants to merge 1 commit into
openai:mainfrom
meichuanyi:docs/add-faq-section

Conversation

@meichuanyi
Copy link
Copy Markdown

Summary

Add a Frequently Asked Questions section to the README to help new users quickly find answers to common setup and usage questions.

Changes

  • Added FAQ section covering: LLM provider support, rate limiting, API key requirements, sandbox agents, agents-as-tools vs handoffs, debugging/tracing, production readiness, and community resources
  • Positioned before the Acknowledgements section for natural flow

Motivation

New users frequently ask about provider support, rate limits, sandbox agents, and debugging. A FAQ section in the README reduces friction and directs users to the right resources.

Checklist

  • Documentation-only change
  • Content is accurate and relevant to the SDK
  • Follows existing README style and formatting

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: b4cd2195f3

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread README.md

### How do I handle rate limits?

The SDK includes built-in retry logic with exponential backoff. You can customize retry behavior via the `RunConfig` by setting `max_retries` and configuring the underlying HTTP client. For high-throughput scenarios, consider implementing request queuing or batching.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Use supported retry settings in rate-limit FAQ

This guidance points users to RunConfig(max_retries=...), but RunConfig does not expose a max_retries field (see src/agents/run_config.py), so following it will raise a constructor error instead of configuring retries. Retry tuning is currently done through model retry settings (for example ModelSettings/ModelRetrySettings) and provider client configuration, so this FAQ answer sends users to a non-functional API path.

Useful? React with 👍 / 👎.

@Adahama0011
Copy link
Copy Markdown

Summary

Add a Frequently Asked Questions section to the README to help new users quickly find answers to common setup and usage questions.

Changes

  • Added FAQ section covering: LLM provider support, rate limiting, API key requirements, sandbox agents, agents-as-tools vs handoffs, debugging/tracing, production readiness, and community resources
  • Positioned before the Acknowledgements section for natural flow

Motivation

New users frequently ask about provider support, rate limits, sandbox agents, and debugging. A FAQ section in the README reduces friction and directs users to the right resources.

Checklist

  • Documentation-only change
  • Content is accurate and relevant to the SDK
  • Follows existing README style and formatting

@seratch
Copy link
Copy Markdown
Member

seratch commented Apr 26, 2026

Thanks for the suggestion, but we prefer covering topics like these on the documentation side rather than README.

@seratch seratch closed this Apr 26, 2026
@Adahama0011
Copy link
Copy Markdown

Frequently Asked Questions (FAQ)

  1. Can Green’s Cafe handle large orders for organizations like banks or schools?
    Yes, we are fully equipped to handle bulk meal production while maintaining quality and timely delivery.
  2. Is the menu fixed or customizable?
    Our menu is flexible. We can tailor meals based on your organization’s preferences, budget, and dietary needs.
  3. How do you ensure food quality and hygiene?
    We follow strict hygiene standards in food preparation, storage, and delivery to ensure safety and quality at all times.
  4. What is your delivery timeline?
    Delivery schedules are agreed upon in advance, and we ensure punctual service for all orders.
  5. Do you offer long-term partnership packages?
    Yes, we provide special pricing and structured plans for long-term contracts with organizations.
  6. What happens in case of service issues?
    We maintain open communication and resolve any issues quickly to ensure client satisfaction.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants